[SPARK-54622][SQL] Promote RequiresDistributionAndOrdering and its required interfaces to Evolving
#53361
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
WDYT, @aokolnychyi , as the author of these interfaces? |
…required interfaces to `Evolving`
dongjoon-hyun
force-pushed
the
SPARK-54622
branch
from
ee61bc3 to
11403e5
Compare
Member
Author
|
Gentle ping, @aokolnychyi . |
Member
Author
|
Could you review this PR, @peter-toth ? |
peter-toth
approved these changes
Dec 7, 2025
Contributor
peter-toth
left a comment
peter-toth
left a comment
There was a problem hiding this comment.
Thanks @dongjoon-hyun for pinging me.
Yeah, these promotions make sense to me.
Member
Author
|
Thank you so much for your review and approval, @peter-toth . Merged to master for Apache Spark 4.2.0. |
xu20160924
pushed a commit
to xu20160924/spark
that referenced
this pull request
Dec 9, 2025
…required interfaces to `Evolving` ### What changes were proposed in this pull request? This PR aims to promote `RequiresDistributionAndOrdering` and its required interfaces to `Evolving` from `Experimental`. ### Why are the changes needed? Since Apache Spark 3.2.0, `RequiresDistributionAndOrdering` and its required interfaces have been served stably over 5 years like the following. In Apache Spark 4.2.0, we had better promote this to `Evolving` because these are no longer `Experimental`. - apache#30706 | Interface | Description | | - | - | | org.apache.spark.sql.connector.distributions.ClusteredDistribution | Unchange | | org.apache.spark.sql.connector.distributions.Distribution | Unchange | | org.apache.spark.sql.connector.distributions.Distributions | Unchange | | org.apache.spark.sql.connector.distributions.OrderedDistribution | Unchange | | org.apache.spark.sql.connector.distributions.UnspecifiedDistribution | Unchange | | org.apache.spark.sql.connector.expressions.NullOrdering | No Functional Change | | org.apache.spark.sql.connector.expressions.SortDirection | No Functional Change | | org.apache.spark.sql.connector.expressions.SortOrder | Stably Evolving | | org.apache.spark.sql.connector.write.RequiresDistributionAndOrdering | Stably Evolving | ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass the CIs and manual review. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#53361 from dongjoon-hyun/SPARK-54622. Authored-by: Dongjoon Hyun <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR aims to promote
RequiresDistributionAndOrderingand its required interfaces toEvolvingfromExperimental.Why are the changes needed?
Since Apache Spark 3.2.0,
RequiresDistributionAndOrderingand its required interfaces have been served stably over 5 years like the following. In Apache Spark 4.2.0, we had better promote this toEvolvingbecause these are no longerExperimental.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs and manual review.
Was this patch authored or co-authored using generative AI tooling?
No.